<?xml version="1.0" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="..\..\XSLTemplates\ErrorsStyleSheet.xsl"?>
<Error>
<ErrorNumber>15336</ErrorNumber>
<ErrorFamily>Autoloader</ErrorFamily>
<ErrorMessage>
ALE: Timeout waiting for QSPI system to initialize, stepper drive task startup failed
</ErrorMessage>
<AppliesTo>
<UnnumberedList>
<ListItem><Text>Trendsetter_400/800_Auto</Text></ListItem>
</UnnumberedList>
</AppliesTo>
<OperatorAction>
<DescriptionText><text>
Call Creo service and report the exact error message and the conditions that
lead to it.
</text></DescriptionText>
</OperatorAction>
<ServiceInformation>
<DescriptionText><text>
Firmware bug.
</text></DescriptionText>
</ServiceInformation>
<Cause>
This error is caused by a firmware fault. It occurs when the firmware attempts
to initialize the stepper motor before the communication between the firmware
and the TEE-board have been established. This error is used during development
and should never occur in the field. Please report this error to the firmware
designer (currently Juliet Wyles). It would be very useful to know what
conditions caused this error to occur and even more useful to have a diagnostic
monitor log file. If possible, the 'verbose aldrv' setting should be 1 when
generating the log file.
</Cause>
<SeeAlso>
<UnnumberedList>
<Link><LinkAddress>../nvs/verbose_cfg_aldrv.xml</LinkAddress><LinkTitle>NVS: verbose aldrv</LinkTitle></Link>
</UnnumberedList>
</SeeAlso>
<OtherLinks>
<Link><LinkAddress>..\..\ShowAllErrors.htm</LinkAddress><LinkTitle>Firmware 0 Error Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllCommands.htm</LinkAddress><LinkTitle>Firmware 0 Command Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllNVS.htm</LinkAddress><LinkTitle>Firmware 0 NVS Index</LinkTitle></Link>
</OtherLinks>
<Updated>
Updated: Wed Jul 16 19:33:02 2008 PST
</Updated>
<Links>
</Links>
</Error>
